Fixing two issues in RayMarcher and VolumeRendering #133
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request addresses two issues that were identified in the RayMarcher and Volume Rendering code:
Random Order Aggregation in RayMarcher: Previously, the samples were aggregated in random order during the forward pass. To ensure correct calculations of
dL_drays_o
anddL_drays_d
usingrays_a
, I have introduced a sorting mechanism to organize the aggregation process appropriately. Although this fix can be improved using CUDA implementation, it still performs well with reasonable speed.Incorrect Gradient from Opacity: There was a problem with the gradient calculation from Opacity, which has now been rectified. The changes align the gradient calculation with the forward pass, ensuring accurate results. These fixes enhance the functionality and accuracy of the RayMarcher implementation.